Repository navigation
Conversation
Drop the golden file and the sanitizer changes it needed. The test now checks the uploaded size through lakectl output and the stat API, and deletes each large object from the backing store once the subtest ends, since deleting the repository leaves its data in place.
Look up the object's physical address in the cleanup itself, so the large object is removed from storage even if the upload or a later check fails.
|
The compatibility job fails in the new test's cleanup, not in the upload. Both subtests of That is the AWS SDK v2 error for an empty region. The ESTI S3 adapter builds its client with Suggested fix, in the "Run lakectl tests" step: env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+ AWS_REGION: us-east-1
ESTI_AWS_ACCESS_KEY_ID: ${{ secrets.ESTI_AWS_ACCESS_KEY_ID }}An alternative that covers any future caller is to default the region in Side note: since the delete failed, the two 5 GiB objects from run 1460 were left behind under Generated by Claude Code |
The ESTI S3 adapter resolves its region from the environment, and the compatibility job exported none, so deleting the large upload failed with an invalid-region endpoint error. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016H9g6KrGzdcBdLerkWzG8S
TBD